What's Changed

Bugs fixed:

- broken support for `Optional[List]` (but not `Optional[list]`), a narrower case of the problem fixed earlier (issue 216) by neithere, thanks to thorwhalen

Full changelog: https://argh.readthedocs.io/en/latest/changes.html

Full diff: https://github.com/neithere/argh/compare/v0.31.1...v0.31.2

*This text is a brief summary of the full changelog entry: https://argh.readthedocs.io/en/latest/changes.html#version-0-31-1-2024-01-19*

What's Changed

Bugs fixed:

- broken support for type alias `List` (issue 216), thanks to thorwhalen.

Enhancements:

- cleaned up the README, rearranged other documentation.

**Full diff**: https://github.com/neithere/argh/compare/v0.31.0...v0.31.1

What's Changed

This release is a major step forward for Argh. It paves the way to a fully annotations-driven approach where decorators will remain a mere legacy.

*This text is a brief summary of the full changelog entry: https://argh.readthedocs.io/en/latest/changes.html#version-0-31-0-2023-12-30*

Breaking changes:

* The typing hints introspection feature is automatically enabled for any command (function) which does **not** have any arguments specified via `arg` decorator.
* A small change in the legacy argument mapping policy `BY_NAME_IF_HAS_DEFAULT` concerning the order of variadic positional vs. keyword-only arguments.
* Removed the previously deprecated decorator `expects_obj`.

Enhancements:

* Type hints: basic usage to infer argument types (fixes 203) by neithere in https://github.com/neithere/argh/pull/211
* Support realtime output through a pipe (fixes 145) by neithere in https://github.com/neithere/argh/pull/202
* High-level functions `argh.dispatch_command()` and `argh.dispatch_commands()`
now accept a new parameter `old_name_mapping_policy`. 

Deprecated:

- the `namespace` argument in `argh.dispatch()` and `argh.parse_and_resolve()`.
Rationale: continued API cleanup.  It's already possible to mutate the
namespace object between parsing and calling the endpoint; it's unlikely that
anyone would need to specify a custom namespace class or pre-populate it
before parsing.  Please file an issue if you have a valid use case.

Other changes:

- Refactoring.

**Full Diff**: https://github.com/neithere/argh/compare/v0.30.5...v0.31.0

What's Changed
* fix: nargs + list as default value (212) by neithere in https://github.com/neithere/argh/pull/213
(thanks to pioio for bug report)
* feat: argspec guessing: if `nargs` is not specified but the default value is a list, `nargs="*"` is assumed and passed to argparse.

**Full Changelog**: https://github.com/neithere/argh/compare/v0.30.4...v0.30.5

Please refer to the official changelog for more details: https://argh.readthedocs.io/en/latest/changes.html

What's Changed

There were complaints about the lack of a deprecation cycle for the legacy name
mapping policy.  This version addresses the issue:

- The handling introduced in v.0.30.2 (raising an exception for clarity)
is retained for cases when no name mapping policy is specified but function
signature contains defaults in non-kwonly args **and kwonly args are also
defined**::

   def main(alpha, beta=1, *, gamma=2):   error — explicit policy required

In a similar case but when **kwonly args are not defined** Argh now assumes
the legacy name mapping policy (`BY_NAME_IF_HAS_DEFAULT`) and merely issues
a deprecation warning with the same message as the exception mentioned above::

   def main(alpha, beta=2):     `[-b BETA] alpha` + DeprecationWarning

This ensures that most of the old scripts still work the same way despite the
new policy being used by default and enforced in cases when it's impossible
to resolve the mapping conflict.

Please note that this "soft" handling is to be removed in version v0.33
(or v1.0 if the former is not deemed necessary).  The new name mapping policy
will be used by default without warnings, like in v0.30.

— by neithere 

**Full Changelog**: https://github.com/neithere/argh/compare/v0.30.3...v0.30.4

What's Changed
*  fix: regression — `arg` deco failing with underscore in positional arg name (fixes 208) by neithere in https://github.com/neithere/argh/pull/209 (thanks to kaetir for a report with a reproducible example)


**Full Changelog**: https://github.com/neithere/argh/compare/v0.30.2...v0.30.3

What's Changed
* fix: raise exception for non-migrated commands (fixes 206) by neithere (reported and valuable feedback given by valentin-feron) in https://github.com/neithere/argh/pull/207

**Full Changelog**: https://github.com/neithere/argh/compare/v0.30.1...v0.30.2

What's Changed

Bugs fixed:

- Regression: certain special values in argument default value would cause an exception (204 reported by mfussenegger, fixed by neithere)

Enhancements:

- Improved the tutorial by neithere 
- Added a more informative error message when the reason is likely to be related to the migration from Argh v0.29 to a version with a new argument name mapping policy by neithere 

Other changes:

- Added `py.typed` marker file for PEP-561 by neithere 

Details

Commits: https://github.com/neithere/argh/compare/v0.30.0...v0.30.1

Full changelog: https://argh.readthedocs.io/en/latest/changes.html#version-0-30-1

What's Changed
* Remove previously deprecated code (closes 184) by neithere in https://github.com/neithere/argh/pull/188
* Type annotations for existing code (closes 185) by neithere in https://github.com/neithere/argh/pull/189
* Deprecate `help` command alias and `expects_obj` decorator by neithere in https://github.com/neithere/argh/pull/192
* Document usage with class methods (closes 138) by neithere in https://github.com/neithere/argh/pull/194
* Remove pre_call, expose finer control over dispatching (re 63) by neithere in https://github.com/neithere/argh/pull/193
* Add support for Python 3.12 (closes 196) by neithere in https://github.com/neithere/argh/pull/195
* Refactor assembling module (closes 197) by neithere in https://github.com/neithere/argh/pull/198
* Keyword-only arguments as options (closes 191) by neithere in https://github.com/neithere/argh/pull/199

**Full Changelog**: https://github.com/neithere/argh/compare/v0.29.4...v0.30.0

What's Changed
* Remove previously deprecated code (closes 184) by neithere in https://github.com/neithere/argh/pull/188
* Type annotations for existing code (closes 185) by neithere in https://github.com/neithere/argh/pull/189
* Deprecate `help` command alias and `expects_obj` decorator by neithere in https://github.com/neithere/argh/pull/192
* Document usage with class methods (closes 138) by neithere in https://github.com/neithere/argh/pull/194
* Remove pre_call, expose finer control over dispatching (re 63) by neithere in https://github.com/neithere/argh/pull/193
* Add support for Python 3.12 (closes 196) by neithere in https://github.com/neithere/argh/pull/195
* Refactor assembling module (closes 197) by neithere in https://github.com/neithere/argh/pull/198
* Keyword-only arguments as options (closes 191) by neithere in https://github.com/neithere/argh/pull/199

**Full Changelog**: https://github.com/neithere/argh/compare/v0.29.4...v0.30.0-alpha

Bugs fixed:

- Test coverage reported as <100% when argcomplete is installed (187)

This is a technical release for packaging purposes.

This is a technical release for packaging purposes.

This is a technical release for packaging purposes.

What's Changed

Backwards incompatible changes:

* Wrapped exceptions now cause ``dispatching.dispatch()`` to raise ``SystemExit(1)``
instead of returning without error. For most users, this means failed commands
will now exit with a failure status instead of a success (by ekimekim in 161).

Deprecated:

* Renamed arguments in `add_commands()` (165 / 178):

- `namespace` → `group_name`
- `namespace_kwargs` → `group_kwargs`

The old names are deprecated and will be removed in v.0.30.

Enhancements:

* Can control exit status (see Backwards Incompatible Changes above) when raising
``CommandError`` using the ``code`` keyword arg.

Bugs fixed:

*  Positional arguments should not lead to removal of short form of keyword argument by neithere in 181

Other changes:

* Avoid depending on iocapture by using pytest's built-in feature by mr-c in 177
* chore: publishing to prod PyPI by neithere in 173
* test: add coverage for action="count" (127) by neithere in 183

New Contributors
* ekimekim made their first contribution in https://github.com/neithere/argh/pull/161
* mr-c made their first contribution in https://github.com/neithere/argh/pull/177

**Full Changelog**: https://github.com/neithere/argh/compare/v0.28.1...v0.29.0

What's Changed
* Add Github workflow to publish the release to PyPI by neithere in https://github.com/neithere/argh/pull/167
* fix: argcomplete-related test by neithere in 172 (reported in 169 by kloczek)
* fix: assumed prog name in tests by neithere in 171 (reported in 170 by mgorny)

**Full Changelog**: https://github.com/neithere/argh/compare/v0.28.0...v0.28.1

Thanks to everyone who reported

A major modernisation and cleanup.

Backward incompatible changes:

- Dropped support for Python 2.7 and 3.7.

Deprecated features, to be removed in v.0.30:

- `argh.assembling.SUPPORTS_ALIASES`.

- Always `True` for recent versions of Python.

- `argh.io.safe_input()` AKA `argh.interaction.safe_input()`.

- Not relevant anymore.  Please use the built-in `input()` instead.

- argument `pre_call` in `dispatch()`.

Even though this hack seems to have been used in some projects, it was never part of the official API and never recommended.

Describing your use case in the discussion about shared arguments (63) can help improve the library to accomodate it in a proper way.

- Argument help as annotations.

- Annotations will only be used for types after v.0.30.
- Please replace any instance of:
 
 def func(foo: "Foobar"):
 
 with the following::
 
 arg('-f', '--foo', help="Foobar")
 def func(foo):
 
 It will be decided later how to keep this functionality "DRY" (don't repeat yourself) without conflicts with modern conventions and tools.

- Added deprecation warnings for some arguments deprecated back in v.0.26.

**Full Changelog**: https://github.com/neithere/argh/compare/v0.27.2...v0.28.0

Minor packaging fix:

* chore: include file required by tox.ini in the sdist (155)

Minor building and packaging fixes:

* docs: add Read the Docs config (160)
* chore: include tox.ini in the sdist (155)

Contributors:

mtelka (155)

This is the last version to support Python 2.7.

Backward incompatible changes:

- Dropped support for Python 2.6.

Enhancements:

- Added support for Python 3.7 through 3.11.
- Support introspection of function signature behind the `wraps` decorator (issue 111).

Fixed bugs:

- When command function signature contained ``**kwargs`` *and* positionals without defaults and with underscores in their names, a weird behaviour could be observed (issue 104).
- Fixed introspection through decorators (issue 111).
- Switched to Python's built-in `unittest.mock` (PR 154).
- Fixed bug with `skip_unknown_args=True` (PR 134).
- Fixed tests for Python 3.9.7+ (issue 148).

Other changes:

- Included the license files in manifest (PR 112).
- Extended the list of similar projects (PR 87).
- Fixed typos and links in documentation (PR 110, 116, 156).
- Switched CI to Github Actions (PR 153).

Contributors:

dwf (105), jwilk (110), jakirkham (112), brilee, sanga (116), Gidgidonihah (134), mrdavidlaing (153), jelly (154), mtelka (154), hugovk (reviewing PRs).

This is a maintenance release. Just a few changes:
- Removed official support for Python 3.4, added for 3.5.
- Various tox-related improvements for development.
- Improved documentation.

This release is intended to be the last one before 1.0. Therefore a major cleanup was done. This **breaks backward compatibility**. If your code is really outdated, please read this list carefully and grep your code.
- Removed decorator `alias` (deprecated since v.0.19).
- Removed decorator `plain_signature` (deprecated since v.0.20).
- Dropped support for old-style functions that implicitly expected namespace objects (deprecated since v.0.21). The `expects_obj` decorator is now mandatory for such functions.
- Removed decorator `command` (deprecated since v.0.21).
- The `wrap_errors` decorator now strictly requires that the error classes
are given as a list (old behaviour was deprecated since v.0.22).
- The `allow_warnings` argument is removed from
`argh.completion.autocomplete()`. Debug-level logging is used instead.
(The warnings were deprecated since v.0.25).

Some more stuff has been scheduled **to be purged before 1.0**:
- Deprecated arguments `title`, `help` and `description` in `add_commands()` helper function. See documentation and issue 60.

Other changes:
- Improved representation of default values in the help.
- Dispatcher can be configured to skip unknown arguments (issue 57).
- Added `add_subcommands()` helper function (a convenience wrapper
for `add_commands()`).
- `EntryPoint` now stores kwargs for the parser.
- Added support for default command _with_ nested commands (issue 78).
This only works with Python 3.4+ due to incorrect behaviour or earlier
versions of Argparse (including the stand-alone one as of 1.2.1).
Due to argparse peculiarities the function assignment technique relies
on a special `ArghNamespace` object. It is used by default in `ArghParser`
and the shortcuts, but if you call the vanilla `ArgumentParser.parse_args()`
method, you now _have_ to supply the proper namespace object.

Fixed bugs:
- Help formatter was broken for arguments with empty strings as default values
(issue 76).

- Added EntryPoint class as another way to assemble functions (see 59).
- Added support for Python 3.4; dropped support for Python 3.3
(this doesn't mean that Argh is necessarily broken under 3.3,
it's just that I'm not testing against it anymore).
- Shell completion warnings are now deprecated in favour of `logging`.
- The command help now displays default values of all arguments (see 64).
- Function docstrings are now displayed verbatim in the help (see 64).
- Argh's dispatching now should work properly in Cython.

Adds support for running chardet CLI via `python -m chardet` (0e9b7bc20366163efcc221281201baff4100fe19, dan-blanchard)

Features
- Add `should_rename_legacy` argument to most functions, which will rename older encodings to their more modern equivalents (e.g., `GB2312` becomes `GB18030`) (264, dan-blanchard)
- Add capital letter sharp S and ISO-8859-15 support (222, SimonWaldherr)
- Add a prober for MacRoman encoding (5 updated as c292b52a97e57c95429ef559af36845019b88b33, Rob Speer and dan-blanchard )
- Add `--minimal` flag to `chardetect` command (214, dan-blanchard)
- Add type annotations to the project and run mypy on CI (261, jdufresne)
- Add support for Python 3.11 (274, hugovk)

Fixes
- Clarify LGPL version in License trove classifier (255, musicinmybrain)
- Remove support for EOL Python 3.6 (260, jdufresne)
- Remove unnecessary guards for non-falsey values (259, jdufresne)

Misc changes
- Switch to Python 3.10 release in GitHub actions (257, jdufresne)
- Remove setup.py in favor of build package (262, jdufresne)
- Run tests on macos, Windows, and 3.11-dev (267, dan-blanchard)

⚠️ This release is the first release of chardet that no longer supports Python < 3.6 ⚠️

In addition to that change, it features the following user-facing changes:

- Added a prober for Johab Korean (207, grizlupo)
- Added a prober for UTF-16/32 BE/LE (109, 206, jpz) 
- Added test data for Croatian, Czech, Hungarian, Polish, Slovak, Slovene, Greek, and Turkish, which should help prevent future errors with those languages
- Improved XML tag filtering, which should improve accuracy for XML files (208)
- Tweaked `SingleByteCharSetProber` confidence to match latest uchardet (209)
- Made `detect_all` return child prober confidences (210)
- Updated examples in docs (223, domdfcoding)
- Documentation fixes (212, 224, 225, 226, 220, 221, 244 from too many to mention)
- Minor performance improvements (252, deedy5)
- Add support for Python 3.10 when testing (232, jdufresne)
- Lots of little development cycle improvements, mostly thanks to jdufresne

Benchmarking chardet 4.0.0 on CPython 3.7.5 (default, Sep  8 2020, 12:19:42)
[Clang 11.0.3 (clang-1103.0.32.62)]
--------------------------------------------------------------------------------
.......................................................................................................................................................................................................................................................................................................................................................................
Calls per second for each encoding:

This minor bugfix release just fixes some packaging and documentation issues:

-  Fix issue with `setup.py` where `pytest_runner` was always being installed. (PR 119, thanks zmedico)
-  Make sure `test.py` is included in the manifest (PR 118, thanks zmedico)
-  Fix a bunch of old URLs in the README and other docs. (PRs 123 and 129, thanks qfan and jdufresne)
-  Update documentation to no longer imply we test/support Python 3 versions before 3.3 (PR 130, thanks jdufresne)

This release fixes a crash when debugging logging was enabled.  (Issue 115, PRs 117 and 125)

Fixes an issue where `detect` would sometimes return `None` instead of a `dict` with the keys `encoding`, `language`, and `confidence` (Issue 113, PR 114).

This bugfix release fixes a crash in the EUC-TW prober when it encountered certain strings (Issue 67).

This release is long overdue, but still mostly serves as a placeholder for the impending 4.0.0 release, which will have retrained models for better accuracy.  For now, this release will get the following improvements up on PyPI:

-  Added support for Turkish ISO-8859-9 detection (PR 41, thanks queeup)
-  Commented out large unused sections of Big5 and EUC-KR tables to save memory (8bc4b89)
-  Removed Python 3.2 from testing, but add 3.4 - 3.6
-  Ensure that stdin is open with mode `'rb'` for `chardetect` CLI. (PR 38, thanks lpsinger)
-  Fixed `chardetect` crash with non-ascii file names (PR 39, thanks nkanaev)
-  Made naming conventions more Pythonic throughout (no more `mTypicalPositiveRatio`, and instead `typical_positive_ratio`)
-  Modernized test scripts and infrastructure so we've got Travis testing and all that stuff
-  Rename `filter_without_english_words` to `filter_international_words` and make it match current Mozilla implementation (PR 44, thanks rsnair2)
-  Updated `filter_english_letters` to match C implementation (c6654595)
-  Temporarily disabled Hungarian ISO-8859-2 and Windows-1250 detection because it is very inaccurate (da6c0a079)
-  Allow CLI sub-package to be importable (PR 55)
-  Add a `hypotheis`-based test (PR 66, thanks DRMacIver)
-  Strip endianness from UTF with BOM predictions so that the encoding can be passed directly to `bytes.decode()` (PR 73, thanks snoack)
-  Fixed broken links in docs (PR 90, thanks roskakori)
-  Added early exit to `chardetect` when encoding is detected instead of looping through entire file (PR 103, thanks jpz)
-  Use `bytearray` objects internally instead of `wrap_ord` calls, which provides a nice performance boost across the board (PR 106)
-  Add `language` property to probers and `UniversalDetector` results (PR 180)
-  Mark the 5 known test failures as such so we can have more useful Travis build results in the meantime (d588407)

In this release, we:
- Added support for CP932 detection (thanks to hashy).
- Fixed an issue where UTF-8 with a BOM would not be detected as UTF-8-SIG (8).
- Modified `chardetect` to use `argparse` for argument parsing.
- Moved docs to a `gh-pages` branch.  You can now access them at http://chardet.github.io.

Fix missing paren in chardetect.py

First version after merger with charade. Loads of little changes.

-   Python 3.13.0a3 is supported.
-   Fix: the JSON report now includes an explicit format version number, closing [issue 1732](https://github.com/nedbat/coveragepy/issues/1732).


:arrow_right:  PyPI page: [coverage 7.4.1](https://pypi.org/project/coverage/7.4.1).
:arrow_right:  To install: `python3 -m pip install coverage==7.4.1`

-   In Python 3.12 and above, you can try an experimental core based on the new `sys.monitoring <python:sys.monitoring>` module by defining a `COVERAGE_CORE=sysmon` environment variable. This should be faster for line coverage, but not for branch coverage, and plugins and dynamic contexts are not yet supported with it. I am very interested to hear how it works (or doesn't!) for you.


:arrow_right:  PyPI page: [coverage 7.4.0](https://pypi.org/project/coverage/7.4.0).
:arrow_right:  To install: `python3 -m pip install coverage==7.4.0`

-   Fix: the change for multi-line signature exclusions in 7.3.3 broke other forms of nested clauses being excluded properly. This is now fixed, closing [issue 1713](https://github.com/nedbat/coveragepy/issues/1713).
-   Fix: in the HTML report, selecting code for copying won't select the line numbers also. Thanks, [Robert Harris](https://github.com/nedbat/coveragepy/pull/1717).


:arrow_right:  PyPI page: [coverage 7.3.4](https://pypi.org/project/coverage/7.3.4).
:arrow_right:  To install: `python3 -m pip install coverage==7.3.4`

-   Fix: function definitions with multi-line signatures can now be excluded by matching any of the lines, closing [issue 684](https://github.com/nedbat/coveragepy/issues/684). Thanks, [Jan Rusak, Maciej Kowalczyk and Joanna Ejzel](https://github.com/nedbat/coveragepy/pull/1705).
-   Fix: XML reports could fail with a TypeError if files had numeric components that were duplicates except for leading zeroes, like `file1.py` and `file001.py`. Fixes [issue 1709](https://github.com/nedbat/coveragepy/issues/1709).
-   The `coverage annotate` command used to announce that it would be removed in a future version. Enough people got in touch to say that they use it, so it will stay. Don't expect it to keep up with other new features though.
-   Added new `debug options <cmd_run_debug>`:
 -   `pytest` writes the pytest test name into the debug output.
 -   `dataop2` writes the full data being added to CoverageData objects.


:arrow_right:  PyPI page: [coverage 7.3.3](https://pypi.org/project/coverage/7.3.3).
:arrow_right:  To install: `python3 -m pip install coverage==7.3.3`

-   The `coverage lcov` command ignored the `[report] exclude_lines` and `[report] exclude_also` settings ([issue 1684](https://github.com/nedbat/coveragepy/issues/1684)). This is now fixed, thanks [Jacqueline Lee](https://github.com/nedbat/coveragepy/pull/1685).
-   Sometimes SQLite will create journal files alongside the coverage.py database files. These are ephemeral, but could be mistakenly included when combining data files. Now they are always ignored, fixing [issue 1605](https://github.com/nedbat/coveragepy/issues/1605). Thanks to Brad Smith for suggesting fixes and providing detailed debugging.
-   On Python 3.12+, we now disable SQLite writing journal files, which should be a little faster.
-   The new 3.12 soft keyword `type` is properly bolded in HTML reports.
-   Removed the "fullcoverage" feature used by CPython to measure the coverage of early-imported standard library modules. CPython [stopped using it](https://github.com/python/cpython/issues/88054) in 2021, and it stopped working completely in Python 3.13.


:arrow_right:  PyPI page: [coverage 7.3.2](https://pypi.org/project/coverage/7.3.2).
:arrow_right:  To install: `python3 -m pip install coverage==7.3.2`

-   The semantics of stars in file patterns has been clarified in the docs. A leading or trailing star matches any number of path components, like a double star would. This is different than the behavior of a star in the middle of a pattern. This discrepancy was [identified by Sviatoslav Sydorenko](https://github.com/nedbat/coveragepy/issues/1407#issuecomment-1631085209), who [provided patient detailed diagnosis](https://github.com/nedbat/coveragepy/pull/1650) and graciously agreed to a pragmatic resolution.
-   The API docs were missing from the last version. They are now [restored](https://coverage.readthedocs.io/en/latest/api_coverage.html).


:arrow_right:  PyPI page: [coverage 7.3.1](https://pypi.org/project/coverage/7.3.1).
:arrow_right:  To install: `python3 -m pip install coverage==7.3.1`

-   Added a `.Coverage.collect` context manager to start and stop coverage data collection.
-   Dropped support for Python 3.7.
-   Fix: in unusual circumstances, SQLite cannot be set to asynchronous mode. Coverage.py would fail with the error `Safety level may not be changed inside a transaction.` This is now avoided, closing [issue 1646](https://github.com/nedbat/coveragepy/issues/1646). Thanks to Michael Bell for the detailed bug report.
-   Docs: examples of configuration files now include separate examples for the different syntaxes: .coveragerc, pyproject.toml, setup.cfg, and tox.ini.
-   Fix: added `nosemgrep` comments to our JavaScript code so that semgrep-based SAST security checks won't raise false alarms about security problems that aren't problems.
-   Added a CITATION.cff file, thanks to [Ken Schackart](https://github.com/nedbat/coveragepy/pull/1641).


:arrow_right:  PyPI page: [coverage 7.3.0](https://pypi.org/project/coverage/7.3.0).
:arrow_right:  To install: `python3 -m pip install coverage==7.3.0`

-   Fix: reverted a [change from 6.4.3](https://github.com/nedbat/coveragepy/pull/1347) that helped Cython, but also increased the size of data files when using dynamic contexts, as described in the now-fixed [issue 1586](https://github.com/nedbat/coveragepy/issues/1586). The problem is now avoided due to a recent change ([issue 1538](https://github.com/nedbat/coveragepy/issues/1538)). Thanks to [Anders Kaseorg](https://github.com/nedbat/coveragepy/pull/1629) and David Szotten for persisting with problem reports and detailed diagnoses.
-   Wheels are now provided for CPython 3.12.


:arrow_right:  PyPI page: [coverage 7.2.7](https://pypi.org/project/coverage/7.2.7).
:arrow_right:  To install: `python3 -m pip install coverage==7.2.7`

-   Fix: the `lcov` command could raise an IndexError exception if a file is translated to Python but then executed under its own name. Jinja2 does this when rendering templates. Fixes [issue 1553](https://github.com/nedbat/coveragepy/issues/1553).
-   Python 3.12 beta 1 now inlines comprehensions. Previously they were compiled as invisible functions and coverage.py would warn you if they weren't completely executed. This no longer happens under Python 3.12.
-   Fix: the `coverage debug sys` command includes some environment variables in its output. This could have included sensitive data. Those values are now hidden with asterisks, closing [issue 1628](https://github.com/nedbat/coveragepy/issues/1628).


:arrow_right:  PyPI page: [coverage 7.2.6](https://pypi.org/project/coverage/7.2.6).
:arrow_right:  To install: `python3 -m pip install coverage==7.2.6`

-   Fix: `html_report()` could fail with an AttributeError on `isatty` if run in an unusual environment where sys.stdout had been replaced. This is now fixed.


:arrow_right:  PyPI page: [coverage 7.2.5](https://pypi.org/project/coverage/7.2.5).
:arrow_right:  To install: `python3 -m pip install coverage==7.2.5`

PyCon 2023 sprint fixes!

-   Fix: with `relative_files = true`, specifying a specific file to include or omit wouldn't work correctly ([issue 1604](https://github.com/nedbat/coveragepy/issues/1604)). This is now fixed, with testing help by [Marc Gibbons](https://github.com/nedbat/coveragepy/pull/1608).
-   Fix: the XML report would have an incorrect `<source>` element when using relative files and the source option ended with a slash ([issue 1541](https://github.com/nedbat/coveragepy/issues/1541)). This is now fixed, thanks to [Kevin Brown-Silva](https://github.com/nedbat/coveragepy/pull/1608).
-   When the HTML report location is printed to the terminal, it's now a terminal-compatible URL, so that you can click the location to open the HTML file in your browser. Finishes [issue 1523](https://github.com/nedbat/coveragepy/issues/1523) thanks to [Ricardo Newbery](https://github.com/nedbat/coveragepy/pull/1613).
-   Docs: a new `Migrating page <migrating>` with details about how to migrate between major versions of coverage.py. It currently covers the wildcard changes in 7.x. Thanks, [Brian Grohe](https://github.com/nedbat/coveragepy/pull/1610).


:arrow_right:  PyPI page: [coverage 7.2.4](https://pypi.org/project/coverage/7.2.4).
:arrow_right:  To install: `python3 -m pip install coverage==7.2.4`

-   Fix: the `config_run_sigterm` setting was meant to capture data if a process was terminated with a SIGTERM signal, but it didn't always. This was fixed thanks to [Lewis Gaul](https://github.com/nedbat/coveragepy/pull/1600), closing [issue 1599](https://github.com/nedbat/coveragepy/issues/1599).
-   Performance: HTML reports with context information are now much more compact. File sizes are typically as small as one-third the previous size, but can be dramatically smaller. This closes [issue 1584](https://github.com/nedbat/coveragepy/issues/1584) thanks to [Oleh Krehel](https://github.com/nedbat/coveragepy/pull/1587).
-   Development dependencies no longer use hashed pins, closing [issue 1592](https://github.com/nedbat/coveragepy/issues/1592).


:arrow_right:  PyPI page: [coverage 7.2.3](https://pypi.org/project/coverage/7.2.3).
:arrow_right:  To install: `python3 -m pip install coverage==7.2.3`

-   Fix: if a virtualenv was created inside a source directory, and a sourced package was installed inside the virtualenv, then all of the third-party packages inside the virtualenv would be measured. This was incorrect, but has now been fixed: only the specified packages will be measured, thanks to [Manuel Jacob](https://github.com/nedbat/coveragepy/pull/1560).
-   Fix: the `coverage lcov` command could create a .lcov file with incorrect LF (lines found) and LH (lines hit) totals. This is now fixed, thanks to [Ian Moore](https://github.com/nedbat/coveragepy/pull/1583).
-   Fix: the `coverage xml` command on Windows could create a .xml file with duplicate `<package>` elements. This is now fixed, thanks to [Benjamin Parzella](https://github.com/nedbat/coveragepy/pull/1574), closing [issue 1573](https://github.com/nedbat/coveragepy/issues/1573).


:arrow_right:  PyPI page: [coverage 7.2.2](https://pypi.org/project/coverage/7.2.2).
:arrow_right:  To install: `python3 -m pip install coverage==7.2.2`

-   Fix: the PyPI page had broken links to documentation pages, but no longer does, closing [issue 1566](https://github.com/nedbat/coveragepy/issues/1566).
-   Fix: public members of the coverage module are now properly indicated so that mypy will find them, fixing [issue 1564](https://github.com/nedbat/coveragepy/issues/1564).


:arrow_right:  PyPI page: [coverage 7.2.1](https://pypi.org/project/coverage/7.2.1).
:arrow_right:  To install: `python3 -m pip install coverage==7.2.1`

-   Added a new setting `[report] exclude_also` to let you add more exclusions without overwriting the defaults. Thanks, [Alpha Chen](https://github.com/nedbat/coveragepy/pull/1557), closing [issue 1391](https://github.com/nedbat/coveragepy/issues/1391).
-   Added a `.CoverageData.purge_files` method to remove recorded data for a particular file. Contributed by [Stephan Deibel](https://github.com/nedbat/coveragepy/pull/1547).
-   Fix: when reporting commands fail, they will no longer congratulate themselves with messages like "Wrote XML report to file.xml" before spewing a traceback about their failure.
-   Fix: arguments in the public API that name file paths now accept pathlib.Path objects. This includes the `data_file` and `config_file` arguments to the Coverage constructor and the `basename` argument to CoverageData. Closes [issue 1552](https://github.com/nedbat/coveragepy/issues/1552).
-   Fix: In some embedded environments, an IndexError could occur on stop() when the originating thread exits before completion. This is now fixed, thanks to [Russell Keith-Magee](https://github.com/nedbat/coveragepy/pull/1543), closing [issue 1542](https://github.com/nedbat/coveragepy/issues/1542).
-   Added a `py.typed` file to announce our type-hintedness. Thanks, [KotlinIsland](https://github.com/nedbat/coveragepy/pull/1550).


:arrow_right:  PyPI page: [coverage 7.2.0](https://pypi.org/project/coverage/7.2.0).
:arrow_right:  To install: `python3 -m pip install coverage==7.2.0`

-   Added: the debug output file can now be specified with `[run] debug_file` in the configuration file. Closes [issue 1319](https://github.com/nedbat/coveragepy/issues/1319).
-   Performance: fixed a slowdown with dynamic contexts that's been around since 6.4.3. The fix closes [issue 1538](https://github.com/nedbat/coveragepy/issues/1538). Thankfully this doesn't break the [Cython change](https://github.com/nedbat/coveragepy/pull/1347) that fixed [issue 972](https://github.com/nedbat/coveragepy/issues/972). Thanks to Mathieu Kniewallner for the deep investigative work and comprehensive issue report.
-   Typing: all product and test code has type annotations.


:arrow_right:  PyPI page: [coverage 7.1.0](https://pypi.org/project/coverage/7.1.0).
:arrow_right:  To install: `python3 -m pip install coverage==7.1.0`

-   Fix: On Python 3.7, a file with type annotations but no `from __future__ import annotations` would be missing statements in the coverage report. This is now fixed, closing [issue 1524](https://github.com/nedbat/coveragepy/issues/1524).


:arrow_right:  PyPI page: [coverage 7.0.5](https://pypi.org/project/coverage/7.0.5).
:arrow_right:  To install: `python3 -m pip install coverage==7.0.5`

-   Performance: an internal cache of file names was accidentally disabled, resulting in sometimes drastic reductions in performance. This is now fixed, closing [issue 1527](https://github.com/nedbat/coveragepy/issues/1527). Thanks to Ivan Ciuvalschii for the reproducible test case.


:arrow_right:  PyPI page: [coverage 7.0.4](https://pypi.org/project/coverage/7.0.4).
:arrow_right:  To install: `python3 -m pip install coverage==7.0.4`

-   Fix: when using pytest-cov or pytest-xdist, or perhaps both, the combining step could fail with `assert row is not None` using 7.0.2. This was due to a race condition that has always been possible and is still possible. In 7.0.1 and before, the error was silently swallowed by the combining code. Now it will produce a message "Couldn't combine data file" and ignore the data file as it used to do before 7.0.2. Closes [issue 1522](https://github.com/nedbat/coveragepy/issues/1522).


:arrow_right:  PyPI page: [coverage 7.0.3](https://pypi.org/project/coverage/7.0.3).
:arrow_right:  To install: `python3 -m pip install coverage==7.0.3`

-   Fix: when using the `[run] relative_files = True` setting, a relative `[paths]` pattern was still being made absolute. This is now fixed, closing [issue 1519](https://github.com/nedbat/coveragepy/issues/1519).
-   Fix: if Python doesn't provide tomllib, then TOML configuration files can only be read if coverage.py is installed with the `[toml]` extra. Coverage.py will raise an error if TOML support is not installed when it sees your settings are in a .toml file. But it didn't understand that `[tools.coverage]` was a valid section header, so the error wasn't reported if you used that header, and settings were silently ignored. This is now fixed, closing [issue 1516](https://github.com/nedbat/coveragepy/issues/1516).
-   Fix: adjusted how decorators are traced on PyPy 7.3.10, fixing [issue 1515](https://github.com/nedbat/coveragepy/issues/1515).
-   Fix: the `coverage lcov` report did not properly implement the `--fail-under=MIN` option. This has been fixed.
-   Refactor: added many type annotations, including a number of refactorings. This should not affect outward behavior, but they were a bit invasive in some places, so keep your eyes peeled for oddities.
-   Refactor: removed the vestigial and long untested support for Jython and IronPython.


:arrow_right:  PyPI page: [coverage 7.0.2](https://pypi.org/project/coverage/7.0.2).
:arrow_right:  To install: `python3 -m pip install coverage==7.0.2`

-   When checking if a file mapping resolved to a file that exists, we weren't considering files in .whl files. This is now fixed, closing [issue 1511](https://github.com/nedbat/coveragepy/issues/1511).
-   File pattern rules were too strict, forbidding plus signs and curly braces in directory and file names. This is now fixed, closing [issue 1513](https://github.com/nedbat/coveragepy/issues/1513).
-   Unusual Unicode or control characters in source files could prevent reporting. This is now fixed, closing [issue 1512](https://github.com/nedbat/coveragepy/issues/1512).
-   The PyPy wheel now installs on PyPy 3.7, 3.8, and 3.9, closing [issue 1510](https://github.com/nedbat/coveragepy/issues/1510).


:arrow_right:  PyPI page: [coverage 7.0.1](https://pypi.org/project/coverage/7.0.1).
:arrow_right:  To install: `python3 -m pip install coverage==7.0.1`

Nothing new beyond 7.0.0b1.


:arrow_right:  PyPI page: [coverage 7.0.0](https://pypi.org/project/coverage/7.0.0).
:arrow_right:  To install: `python3 -m pip install coverage==7.0.0`

A number of changes have been made to file path handling, including pattern matching and path remapping with the `[paths]` setting (see `config_paths`). These changes might affect you, and require you to update your settings.

(This release includes the changes from [6.6.0b1](https://coverage.readthedocs.io/en/latest/changes.html#changes-6-6-0b1), since 6.6.0 was never released.)

-   Changes to file pattern matching, which might require updating your configuration:
 -   Previously, `*` would incorrectly match directory separators, making precise matching difficult. This is now fixed, closing [issue 1407](https://github.com/nedbat/coveragepy/issues/1407).
 -   Now `**` matches any number of nested directories, including none.
-   Improvements to combining data files when using the `config_run_relative_files` setting, which might require updating your configuration:
 -   During `coverage combine`, relative file paths are implicitly combined without needing a `[paths]` configuration setting. This also fixed [issue 991](https://github.com/nedbat/coveragepy/issues/991).
 -   A `[paths]` setting like `*/foo` will now match `foo/bar.py` so that relative file paths can be combined more easily.
 -   The `config_run_relative_files` setting is properly interpreted in more places, fixing [issue 1280](https://github.com/nedbat/coveragepy/issues/1280).
-   When remapping file paths with `[paths]`, a path will be remapped only if the resulting path exists. The documentation has long said the prefix had to exist, but it was never enforced. This fixes [issue 608](https://github.com/nedbat/coveragepy/issues/608), improves [issue 649](https://github.com/nedbat/coveragepy/issues/649), and closes [issue 757](https://github.com/nedbat/coveragepy/issues/757).
-   Reporting operations now implicitly use the `[paths]` setting to remap file paths within a single data file. Combining multiple files still requires the `coverage combine` step, but this simplifies some single-file situations. Closes [issue 1212](https://github.com/nedbat/coveragepy/issues/1212) and [issue 713](https://github.com/nedbat/coveragepy/issues/713).
-   The `coverage report` command now has a `--format=` option. The original style is now `--format=text`, and is the default.
 -   Using `--format=markdown` will write the table in Markdown format, thanks to [Steve Oswald](https://github.com/nedbat/coveragepy/pull/1479), closing [issue 1418](https://github.com/nedbat/coveragepy/issues/1418).
 -   Using `--format=total` will write a single total number to the output. This can be useful for making badges or writing status updates.
-   Combining data files with `coverage combine` now hashes the data files to skip files that add no new information. This can reduce the time needed. Many details affect the speed-up, but for coverage.py's own test suite, combining is about 40% faster. Closes [issue 1483](https://github.com/nedbat/coveragepy/issues/1483).
-   When searching for completely un-executed files, coverage.py uses the presence of `__init__.py` files to determine which directories have source that could have been imported. However, [implicit namespace packages](https://peps.python.org/pep-0420/) don't require `__init__.py`. A new setting `[report] include_namespace_packages` tells coverage.py to consider these directories during reporting. Thanks to [Felix Horvat](https://github.com/nedbat/coveragepy/pull/1387) for the contribution. Closes [issue 1383](https://github.com/nedbat/coveragepy/issues/1383) and [issue 1024](https://github.com/nedbat/coveragepy/issues/1024).
-   Fixed environment variable expansion in pyproject.toml files. It was overly broad, causing errors outside of coverage.py settings, as described in [issue 1481](https://github.com/nedbat/coveragepy/issues/1481) and [issue 1345](https://github.com/nedbat/coveragepy/issues/1345). This is now fixed, but in rare cases will require changing your pyproject.toml to quote non-string values that use environment substitution.
-   An empty file has a coverage total of 100%, but used to fail with `--fail-under`. This has been fixed, closing [issue 1470](https://github.com/nedbat/coveragepy/issues/1470).
-   The text report table no longer writes out two separator lines if there are no files listed in the table. One is plenty.
-   Fixed a mis-measurement of a strange use of wildcard alternatives in match/case statements, closing [issue 1421](https://github.com/nedbat/coveragepy/issues/1421).
-   Fixed internal logic that prevented coverage.py from running on implementations other than CPython or PyPy ([issue 1474](https://github.com/nedbat/coveragepy/issues/1474)).
-   The deprecated `[run] note` setting has been completely removed.


:arrow_right:  PyPI page: [coverage 7.0.0b1](https://pypi.org/project/coverage/7.0.0b1).
:arrow_right:  To install: `python3 -m pip install coverage==7.0.0b1`

(Note: 6.6.0 final was never released. These changes are part of [7.0.0b1](https://coverage.readthedocs.io/en/latest/changes.html#changes-7-0-0b1).)

-   Changes to file pattern matching, which might require updating your configuration:
 -   Previously, `*` would incorrectly match directory separators, making precise matching difficult. This is now fixed, closing [issue 1407](https://github.com/nedbat/coveragepy/issues/1407).
 -   Now `**` matches any number of nested directories, including none.
-   Improvements to combining data files when using the `config_run_relative_files` setting:
 -   During `coverage combine`, relative file paths are implicitly combined without needing a `[paths]` configuration setting. This also fixed [issue 991](https://github.com/nedbat/coveragepy/issues/991).
 -   A `[paths]` setting like `*/foo` will now match `foo/bar.py` so that relative file paths can be combined more easily.
 -   The setting is properly interpreted in more places, fixing [issue 1280](https://github.com/nedbat/coveragepy/issues/1280).
-   Fixed environment variable expansion in pyproject.toml files. It was overly broad, causing errors outside of coverage.py settings, as described in [issue 1481](https://github.com/nedbat/coveragepy/issues/1481) and [issue 1345](https://github.com/nedbat/coveragepy/issues/1345). This is now fixed, but in rare cases will require changing your pyproject.toml to quote non-string values that use environment substitution.
-   Fixed internal logic that prevented coverage.py from running on implementations other than CPython or PyPy ([issue 1474](https://github.com/nedbat/coveragepy/issues/1474)).


:arrow_right:  PyPI page: [coverage 6.6.0b1](https://pypi.org/project/coverage/6.6.0b1).
:arrow_right:  To install: `python3 -m pip install coverage==6.6.0b1`

-   The JSON report now includes details of which branches were taken, and which are missing for each file. Thanks, [Christoph Blessing](https://github.com/nedbat/coveragepy/pull/1438). Closes [issue 1425](https://github.com/nedbat/coveragepy/issues/1425).
-   Starting with coverage.py 6.2, `class` statements were marked as a branch. This wasn't right, and has been reverted, fixing [issue 1449](https://github.com/nedbat/coveragepy/issues/1449). Note this will very slightly reduce your coverage total if you are measuring branch coverage.
-   Packaging is now compliant with [PEP 517](https://peps.python.org/pep-0517/), closing [issue 1395](https://github.com/nedbat/coveragepy/issues/1395).
-   A new debug option `--debug=pathmap` shows details of the remapping of paths that happens during combine due to the `[paths]` setting.
-   Fix an internal problem with caching of invalid Python parsing. Found by OSS-Fuzz, fixing their [bug 50381](https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50381).


:arrow_right:  PyPI page: [coverage 6.5.0](https://pypi.org/project/coverage/6.5.0).
:arrow_right:  To install: `python3 -m pip install coverage==6.5.0`

-   Wheels are now provided for Python 3.11.


:arrow_right:  PyPI page: [coverage 6.4.4](https://pypi.org/project/coverage/6.4.4).
:arrow_right:  To install: `python3 -m pip install coverage==6.4.4`

-   Fix a failure when combining data files if the file names contained glob-like patterns. Thanks, [Michael Krebs and Benjamin Schubert](https://github.com/nedbat/coveragepy/issues/1405).
-   Fix a messaging failure when combining Windows data files on a different drive than the current directory, closing [issue 1428](https://github.com/nedbat/coveragepy/issues/1428). Thanks, [Lorenzo Micò](https://github.com/nedbat/coveragepy/pull/1430).
-   Fix path calculations when running in the root directory, as you might do in a Docker container. Thanks [Arthur Rio](https://github.com/nedbat/coveragepy/issues/1403).
-   Filtering in the HTML report wouldn't work when reloading the index page. This is now fixed. Thanks, [Marc Legendre](https://github.com/nedbat/coveragepy/issues/1413).
-   Fix a problem with Cython code measurement, closing [issue 972](https://github.com/nedbat/coveragepy/issues/972). Thanks, [Matus Valo](https://github.com/nedbat/coveragepy/pull/1347).


:arrow_right:  PyPI page: [coverage 6.4.3](https://pypi.org/project/coverage/6.4.3).
:arrow_right:  To install: `python3 -m pip install coverage==6.4.3`

-   Updated for a small change in Python 3.11.0 beta 4: modules now start with a line with line number 0, which is ignored. This line cannot be executed, so coverage totals were thrown off. This line is now ignored by coverage.py, but this also means that truly empty modules (like `__init__.py`) have no lines in them, rather than one phantom line. Fixes [issue 1419](https://github.com/nedbat/coveragepy/issues/1419).
-   Internal debugging data added to sys.modules is now an actual module, to avoid confusing code that examines everything in sys.modules. Thanks, [Yilei Yang](https://github.com/nedbat/coveragepy/pull/1399).


:arrow_right:  PyPI page: [coverage 6.4.2](https://pypi.org/project/coverage/6.4.2).
:arrow_right:  To install: `python3 -m pip install coverage==6.4.2`

-   Greatly improved performance on PyPy, and other environments that need the pure Python trace function. Thanks, Carl Friedrich Bolz-Tereick ([pull 1381](https://github.com/nedbat/coveragepy/pull/1381) and [pull 1388](https://github.com/nedbat/coveragepy/pull/1388)). Slightly improved performance when using the C trace function, as most environments do. Closes [issue 1339](https://github.com/nedbat/coveragepy/issues/1339).
-   The conditions for using tomllib from the standard library have been made more precise, so that 3.11 alphas will continue to work. Closes [issue 1390](https://github.com/nedbat/coveragepy/issues/1390).


:arrow_right:  PyPI page: [coverage 6.4.1](https://pypi.org/project/coverage/6.4.1).
:arrow_right:  To install: `python3 -m pip install coverage==6.4.1`

-   A new setting, `config_run_sigterm`, controls whether a SIGTERM signal handler is used. In 6.3, the signal handler was always installed, to capture data at unusual process ends. Unfortunately, this introduced other problems (see [issue 1310](https://github.com/nedbat/coveragepy/issues/1310)). Now the signal handler is only used if you opt-in by setting `[run] sigterm = true`.
-   Small changes to the HTML report:
 -   Added links to next and previous file, and more keyboard shortcuts: `[` and `]` for next file and previous file; `u` for up to the index; and `?` to open/close the help panel. Thanks, [J. M. F. Tsang](https://github.com/nedbat/coveragepy/pull/1364).
 -   The time stamp and version are displayed at the top of the report. Thanks, [Ammar Askar](https://github.com/nedbat/coveragepy/pull/1354). Closes [issue 1351](https://github.com/nedbat/coveragepy/issues/1351).
-   A new debug option `debug=sqldata` adds more detail to `debug=sql`, logging all the data being written to the database.
-   Previously, running `coverage report` (or any of the reporting commands) in an empty directory would create a .coverage data file. Now they do not, fixing [issue 1328](https://github.com/nedbat/coveragepy/issues/1328).
-   On Python 3.11, the `[toml]` extra no longer installs tomli, instead using tomllib from the standard library. Thanks [Shantanu](https://github.com/nedbat/coveragepy/pull/1359).
-   In-memory CoverageData objects now properly update(), closing [issue 1323](https://github.com/nedbat/coveragepy/issues/1323).


:arrow_right:  PyPI page: [coverage 6.4](https://pypi.org/project/coverage/6.4).
:arrow_right:  To install: `python3 -m pip install coverage==6.4`

-   Fix: Coverage.py now builds successfully on CPython 3.11 (3.11.0b1) again. Closes [issue 1367](https://github.com/nedbat/coveragepy/issues/1367). Some results for generators may have changed.


:arrow_right:  PyPI page: [coverage 6.3.3](https://pypi.org/project/coverage/6.3.3).
:arrow_right:  To install: `python3 -m pip install coverage==6.3.3`

-   Fix: adapt to pypy3.9's decorator tracing behavior. It now traces function decorators like CPython 3.8: both the -line and the def-line are traced. Fixes [issue 1326](https://github.com/nedbat/coveragepy/issues/1326).
-   Debug: added `pybehave` to the list of `coverage debug <cmd_debug>` and `cmd_run_debug` options.
-   Fix: show an intelligible error message if `--concurrency=multiprocessing` is used without a configuration file. Closes [issue 1320](https://github.com/nedbat/coveragepy/issues/1320).


:arrow_right:  PyPI page: [coverage 6.3.2](https://pypi.org/project/coverage/6.3.2).
:arrow_right:  To install: `python3 -m pip install coverage==6.3.2`

-   Fix: deadlocks could occur when terminating processes. Some of these deadlocks (described in [issue 1310](https://github.com/nedbat/coveragepy/issues/1310)) are now fixed.
-   Fix: a signal handler was being set from multiple threads, causing an error: "ValueError: signal only works in main thread". This is now fixed, closing [issue 1312](https://github.com/nedbat/coveragepy/issues/1312).
-   Fix: `--precision` on the command-line was being ignored while considering `--fail-under`. This is now fixed, thanks to [Marcelo Trylesinski](https://github.com/nedbat/coveragepy/pull/1317).
-   Fix: releases no longer provide 3.11.0-alpha wheels. Coverage.py uses CPython internal fields which are moving during the alpha phase. Fixes [issue 1316](https://github.com/nedbat/coveragepy/issues/1316).


:arrow_right:  PyPI page: [coverage 6.3.1](https://pypi.org/project/coverage/6.3.1).
:arrow_right:  To install: `python3 -m pip install coverage==6.3.1`

-   Feature: Added the `lcov` command to generate reports in LCOV format. Thanks, [Bradley Burns](https://github.com/nedbat/coveragepy/pull/1289). Closes issues [587](https://github.com/nedbat/coveragepy/issues/587) and [626](https://github.com/nedbat/coveragepy/issues/626).
-   Feature: the coverage data file can now be specified on the command line with the `--data-file` option in any command that reads or writes data. This is in addition to the existing `COVERAGE_FILE` environment variable. Closes [issue 624](https://github.com/nedbat/coveragepy/issues/624). Thanks, [Nikita Bloshchanevich](https://github.com/nedbat/coveragepy/pull/1304).
-   Feature: coverage measurement data will now be written when a SIGTERM signal is received by the process. This includes `Process.terminate <python:multiprocessing.Process.terminate>`, and other ways to terminate a process. Currently this is only on Linux and Mac; Windows is not supported. Fixes [issue 1307](https://github.com/nedbat/coveragepy/issues/1307).
-   Dropped support for Python 3.6, which reached end-of-life on 2021-12-23.
-   Updated Python 3.11 support to 3.11.0a4, fixing [issue 1294](https://github.com/nedbat/coveragepy/issues/1294).
-   Fix: the coverage data file is now created in a more robust way, to avoid problems when multiple processes are trying to write data at once. Fixes issues [1303](https://github.com/nedbat/coveragepy/issues/1303) and [883](https://github.com/nedbat/coveragepy/issues/883).
-   Fix: a .gitignore file will only be written into the HTML report output directory if the directory is empty. This should prevent certain unfortunate accidents of writing the file where it is not wanted.
-   Releases now have MacOS arm64 wheels for Apple Silicon, fixing [issue 1288](https://github.com/nedbat/coveragepy/issues/1288).


:arrow_right:  PyPI page: [coverage 6.3](https://pypi.org/project/coverage/6.3).
:arrow_right:  To install: `python3 -m pip install coverage==6.3`

-   Feature: Now the `--concurrency` setting can now have a list of values, so that threads and another lightweight threading package can be measured together, such as `--concurrency=gevent,thread`. Closes [issue 1012](https://github.com/nedbat/coveragepy/issues/1012) and [issue 1082](https://github.com/nedbat/coveragepy/issues/1082).
-   Fix: A module specified as the `source` setting is imported during startup, before the user program imports it. This could cause problems if the rest of the program isn't ready yet. For example, [issue 1203](https://github.com/nedbat/coveragepy/issues/1203) describes a Django setting that is accessed before settings have been configured. Now the early import is wrapped in a try/except so errors then don't stop execution.
-   Fix: A colon in a decorator expression would cause an exclusion to end too early, preventing the exclusion of the decorated function. This is now fixed.
-   Fix: The HTML report now will not overwrite a .gitignore file that already exists in the HTML output directory (follow-on for [issue 1244](https://github.com/nedbat/coveragepy/issues/1244)).
-   API: The exceptions raised by Coverage.py have been specialized, to provide finer-grained catching of exceptions by third-party code.
-   API: Using `suffix=False` when constructing a Coverage object with multiprocessing wouldn't suppress the data file suffix ([issue 989](https://github.com/nedbat/coveragepy/issues/989)). This is now fixed.
-   Debug: The `coverage debug data` command will now sniff out combinable data files, and report on all of them.
-   Debug: The `coverage debug` command used to accept a number of topics at a time, and show all of them, though this was never documented. This no longer works, to allow for command-line options in the future.


:arrow_right:  PyPI page: [coverage 6.2](https://pypi.org/project/coverage/6.2).
:arrow_right:  To install: `python3 -m pip install coverage==6.2`

-   Python 3.11 is supported (tested with 3.11.0a2). One still-open issue has to do with [exits through with-statements](https://github.com/nedbat/coveragepy/issues/1270).
-   Fix: When remapping file paths through the `[paths]` setting while combining, the `[run] relative_files` setting was ignored, resulting in absolute paths for remapped file names ([issue 1147](https://github.com/nedbat/coveragepy/issues/1147)). This is now fixed.
-   Fix: Complex conditionals over excluded lines could have incorrectly reported a missing branch ([issue 1271](https://github.com/nedbat/coveragepy/issues/1271)). This is now fixed.
-   Fix: More exceptions are now handled when trying to parse source files for reporting. Problems that used to terminate coverage.py can now be handled with `[report] ignore_errors`. This helps with plugins failing to read files ([django\_coverage\_plugin issue 78](https://github.com/nedbat/django_coverage_plugin/issues/78)).
-   Fix: Removed another vestige of jQuery from the source tarball ([issue 840](https://github.com/nedbat/coveragepy/issues/840)).
-   Fix: Added a default value for a new-to-6.x argument of an internal class. This unsupported class is being used by coveralls ([issue 1273](https://github.com/nedbat/coveragepy/issues/1273)). Although I'd rather not "fix" unsupported interfaces, it's actually nicer with a default value.


:arrow_right:  PyPI page: [coverage 6.1.2](https://pypi.org/project/coverage/6.1.2).
:arrow_right:  To install: `python3 -m pip install coverage==6.1.2`

-   Fix: The sticky header on the HTML report didn't work unless you had branch coverage enabled. This is now fixed: the sticky header works for everyone. (Do people still use coverage without branch measurement!? j/k)
-   Fix: When using explicitly declared namespace packages, the "already imported a file that will be measured" warning would be issued ([issue 888](https://github.com/nedbat/coveragepy/issues/888)). This is now fixed.


:arrow_right:  PyPI page: [coverage 6.1.1](https://pypi.org/project/coverage/6.1.1).
:arrow_right:  To install: `python3 -m pip install coverage==6.1.1`

-   Deprecated: The `annotate` command and the `Coverage.annotate` function will be removed in a future version, unless people let me know that they are using it. Instead, the `html` command gives better-looking (and more accurate) output, and the `report -m` command will tell you line numbers of missing lines. Please get in touch if you have a reason to use `annotate` over those better options: <nednedbatchelder.com>.
-   Feature: Coverage now sets an environment variable, `COVERAGE_RUN` when running your code with the `coverage run` command. The value is not important, and may change in the future. Closes [issue 553](https://github.com/nedbat/coveragepy/issues/553).
-   Feature: The HTML report pages for Python source files now have a sticky header so the file name and controls are always visible.
-   Feature: The `xml` and `json` commands now describe what they wrote where.
-   Feature: The `html`, `combine`, `xml`, and `json` commands all accept a `-q/--quiet` option to suppress the messages they write to stdout about what they are doing ([issue 1254](https://github.com/nedbat/coveragepy/issues/1254)).
-   Feature: The `html` command writes a `.gitignore` file into the HTML output directory, to p